projects / gtk4.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ff85f6c) | patch
wayland: Don't use g_error() on connection lost
authorOlivier Fourdan <ofourdan@redhat.com>
Fri, 27 Feb 2015 12:06:29 +0000 (13:06 +0100)
committerMatthias Clasen <mclasen@redhat.com>
Fri, 27 Feb 2015 21:26:39 +0000 (16:26 -0500)
commit53028ff3bb0610f5fb4df360391af9ee23f61cfa
treedadc19e40c04bf2b85e46ed9baaaa66fa64c8009tree | snapshot
parentff85f6ce3f838384fb9239e14939d5dbb1f49648commit | diff
wayland: Don't use g_error() on connection lost

When the Wayland compositor vanishes, all applications connected will
receive a SIGPIPE as soon as they try to use wl_display_dispatch().

Do not use g_error() to terminate the applications when this occurs,
g_error() means an error in the application while here it's not truly
the case.

Use g_warning() and exit() instead.

Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
https://bugzilla.gnome.org/show_bug.cgi?id=745289
gdk/wayland/gdkeventsource.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.